Task: Private System Build
Generate a local build of the component or product to validate the development and/or run smoke or unit tests
Disciplines: Build Management
Purpose

Provide feedback to the developer of the changes just implemented in the private workspace.

Relationships
RolesPrimary Performer: Additional Performers:
InputsMandatory:
    		Optional:
    • None
    Outputs
      Main Description

      The Private System Build is used by the individual developer working on an isolated development task to verify the consistency and correctness of their changes before committing them to the codeline where they will be visible to the rest of the development team. The developer creates a Private Workspace and populates it with the latest working versions from the codeline in order to begin work on their development task. After making changes in their Private Workspace, the developer needs to ensure that the source changes work correctly and won't "break the build" for the rest of the team.

      Steps
      Define the build completness

      Define the build completness:
      - Clean full build: The environment should be totally cleaned before the build execution.
      - Incremental build: Other parts from previous build can be reused (It is faster, but less secure) 

      Assure build environment is similar to a release build environment

      The purpose of having a build envinronment equals (or even much similar) to release build envinroment is to avoid future problems in the release generation.

      Launch Build
      Launch Build using the command line with the resolved compile time variabilities if applicable.
      Key Considerations
      This build visibility is only individual.